@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@coliver said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@thwr said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

@IRJ said in Building a First Active Directory Domain Controller on Windows 2012 R2 Core:

Good article. There is ZERO reason to have a GUI on a Domain Controller. Everything can be done through Server Manager on Windows 10/8

You mean RSAT 😉

Both? You can do a lot of directory management through Server Manager as well.

Ok, agree. Just don't like the Server Manager this much, ugly interface. I want to be sure WHICH drive on WHICH host I'm going to format for example. But that is just my personal opinion and I'm more or less a console fetishist 😉

But when it comes to ADSIedit or AD sites, you really want to have RSAT.

huh?

0_1469044083616_2016-07-20_15-47-37.png

Those options are generally only there is RSAT is installed.

@Nara said:

@Bill-Kindle said:

@scottalanmiller said:

It's the only install option that I normally use. I only install the GUI if there is a specific site technical deficiency making it necessary.

It's the default option and the option that is suggested with all new 2012 R2 installs thanks to the Server Manager and PowerShell. The really nice thing is that you can deploy Server Core, and if you so choose at a later date install the full GUI and even revert it back to Core. It's not a irrevocable decision now with 2012.

That has saved me a few times so far.

Up until about a month or so ago I was still afraid of doing this because I thought it was still irrevocable like it was in 2008 R2. After seeing how to switch back and forth with a few PowerShell cmdlets and parameters, I'm going to install and maintain more core systems because I always have RSAT and Server Manager now.